home *** CD-ROM | disk | FTP | other *** search
- Path: mail2news.demon.co.uk!tarik.demon.co.uk
- From: Laurence Barea <larry@tarik.demon.co.uk>
- Newsgroups: comp.lang.c
- Subject: Re: Zombies & Daemons
- Date: Fri, 08 Mar 96 02:15:16 GMT
- Organization: Dialog Systems Limited
- Message-ID: <826251316snz@tarik.demon.co.uk>
- References: <3134348F.7526@citenet.net> <4hgchg$t34@metroux.metrobbs.com>
- Reply-To: larry@tarik.demon.co.uk
- X-NNTP-Posting-Host: tarik.demon.co.uk
- X-Newsreader: Demon Internet Simple News v1.30
- X-Mail2News-Path: tarik.demon.co.uk
-
- In article <4hgchg$t34@metroux.metrobbs.com>
- cakirke@metroux.metrobbs.com "Chris Kirke" writes:
-
- > In article <3134348F.7526@citenet.net>, oliver@citenet.net says...
- > >
- [snip]
- > >
- > > The problem is this: when one of the children dies for whatever
- > >reason (usually a f*cked OCI call which makes the daemons session
- > >unstable), the parent's sigcld handler forks a new child to keep a
- > >consistent number of processes running. For some reason, however, the
- > >dead child process lingers around as a zombie process ... how do I avoid
- > >this?
-
- [snip]
-
- I hope I am remembering this correctly from an HP-UX man page.
- The child will become a zombie if the child exited without the parent
- waiting (wait()) for it to complete.
-
- --
- Laurence Barea
- larry@tarik.demon.co.uk
-